home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-20
/
pctor1.zip
/
DOCS
< prev
next >
Wrap
Text File
|
1991-10-23
|
13KB
|
406 lines
PCTOR V1.03
PCTOR, TORBIOS (c) Johan Forrer KC7WW 1991
Author: Johan B. Forrer KC7WW
26553 Priceview Drive
Monroe, OR 97456
United States of America
Shareware notice
These programs are distributed as Shareware products. You may
freely copy and share the programs with your friends, associates
and other radio amateurs. PCTOR or TORBIOS may not be sold or
distributed with another product without the express written
permission of the author. The author, Johan Forrer, KC7WW will
only support unmodified copies of this software.
If you decide to use any of these products, you should become a
registered user by sending $20.00 or equivalent in foreign
currency together with the completed registration form to the
author. All transactions must be drawn on US banks. Upon receipt
of your registration, you will receive one free update disk
containing the latest release of the software . You will also be
notified of future developments. Improvements are continually
being made and exciting additions are under way or in the process
of being implemented such as a DSP software modem front end for
i486 compatible machines.
If you are not satisfied with the program after registering it,
you have 30 days from your registration date to return it for a
full refund of your money, no questions asked.
Commercial Users please contact Johan Forrer directly for
modifications and/or details of Site licensing.
The helpful suggestions of Frank Gorichar, W7JUF, who beta tested
early versions of this software is greatly appreciated. Helpful
suggestions by Vic Poor, W5SMM was invaluable especially on
compatibility with MBBIOS and PAMS. Thanks to Frank Wyatt, N6FW
for forwarding technical documentation to me.
Please support the efforts of shareware developers.
Table of contents
1.0 PCTOR and TORBIOS what does it do ?
1.1 Requirements to run PCTOR and TORBIOS
1.2 CAUTION
2.0 Introduction
3.0 Hardware Interface
4.0 Installation
4.1 Software
4.2 Customizing the Configuration file
5.0 Operating PCTOR
5.1 Function keys
5.2 Command Menu
6.0 Principle of operation
7.0 Disclaimer
1.0 PCTOR and TORBIOS what does it do ?
PCTOR and TORBIOS makes it possible to run AMTOR without the
investment of a hardware TNC. TORBIOS is the low-level
interface/emulator and PCTOR is a user-interface.
1.1 Requirements to run PCTOR and TORBIOS
An HF modem, i.e. ST-6 or equivalent is required. For
transmission of AMTOR over the air, the user also has to provide
a PTT interface and either AFSK or FSK. These interfaces are
often included in an HF modem. If the software is used for
monitoring only, only the HF modem is required. The HF modem is
required to convert audio tones to RS232 compatible digital
levels required by TORBIOS.
TORBIOS uses some of the signal lines of the standard COM1 or
COM2 serial ports as a digital interface. Later versions of
TORBIOS will implement DSP techniques to perform modem funtions. 1.2 Caution
This software may not be suitable for all working environments.
The user should therefore proceed with the usual caution and make
sure critical software is backed up.
The author has done extensive tests on a very modest PC-
compatible system running an 8 Mhz V20 processor and 20 MB hard
disk. No other potentially competing resident software was used.
Every effort has been made to ensure that the software is "well
behaved", however, the user is reminded that this software relies
on critical timing. It "tricks" the system by speeding the system
timer up to run at an one millisecond interrupt rate and installs
itself in the timer interrupt chain. Normal system timer
functionality is retained, i.e. time-of-day and floppy disk
timeout activities. The user must thus be careful not to run
other software that relies on similar "tricks" as the
consequences is indeterminable.
Normal program usage and program termination will undo the
actions of TORBIOS and restore normal system operation. Should a
program failure occur, the only way to restore normal system
operation is to reboot DOS.
2.0 Introduction
TORBIOS is an implementation of CCIR specification 476-2 on an
IBM personal computer or compatible computer. As such, it
replaces the need for dedicated TNC hardware and is an attractive
alternative for the casual user evaluating a new operating mode,
as well as the serious developer that needs to embed low level
I/O functionality into a system.
PCTOR is a user interface program that works in conjunction with
TORBIOS that enables a user to operate and monitor TOR traffic
with a minimum of fuss. It has a multiple-window user interface.
The keyboard function keys are used to control operations. Split
screen displays shows the progression of the dialogue and the
real-time status of low-level internal functions.
PCTOR was developed using the sophistication of C++ with calls to
TORBIOS, a resident driver that was written in assembly language.
3.0 Hardware interface
TORBIOS interfaces through signals of the COM1 or COM2 RS232
port. The following allocation of RS232 signals have been made:
Other signal pins may be connected, however will play no part in
the operation of PCTOR.
For a 25-pin connector:
pin 20 (DTR) - output data bits (mark -12V, space +12V)
pin 4 (RTS) - PTT (off -12V, on +12V)
pin 8 (DCD) - input data bits (mark +12V, space -12V)
If your RTTY modem and interface requires different logic levels,
these may be configured using either the on-line command menu in
PCTOR, or included in a configuration file "TOR.CNF". An example
has been included. (See below for more details in "customizing
the setup file).
4.0 Installation
4.1 Software
It is assumed that a hard disk is available, though the program
can be run off a floppy disk as well. In fact it is suggested
that you first run off a floppy disk to see if this software is
compatible with other software that you may have on your system.
1. Create a new subdirectory and change directory to it, i.e.
mkdir tor
cd tor
2. Copy the contents of the floppy to the new subdirectory.
copy a:*.*
The following files will be copied:
tor.exe -- The split screen AMTOR program.
tor.cnf -- Setup file to custom configure your program.
tor.doc -- This documentation.
TORBIOS.COM -- COM1 TSR driver.
TORBIOS2.COM -- COM2 TSR driver.
brag.tor -- An example test file to load.
cq.tor -- Another example file to load.
AMTOR.BAT -- A batch file to run TOR with a parameter. Check
to see which communications port COM 1 or 2 you
desire.
3. Customize tor.cnf (see 4.2 Customizing the configuration)
4. Run the program, i.e. type AMTOR
4.2 Customizing the configuration
To enable a user to streamline the setup of the program to his
requirements, a configuration file, "tor.cnf" is read during
startup. Read and edit the contents of the provided file
"tor.cnf" to suit your own preferences. This file is optional,
but when not found, the system will use defaults.
Since TORBIOS is supposed to work with any modem, the logic of
the input/output interface needs to be configurable. This is done
by setting up input and output "masks". There are two bits on the
output mask that need to be set (DTR - used for sending data
bits, and CTS - used for PTT control). On input there is only one
bit level that needs to be set (DCD - used for input data). The
meaning of these masks are as follows:
outmask:0 - normal RTS normal DTR
1 - normal RTS invert DTR
2 - invert RTS normal DTR
3 - invert RTS invert DTR
inmask:0 - normal DCD
1 - invert DCD
As a suggestion, leave the settings as outmask:0 and inmask:0
Until you have sorted out the required logic interfacing logic,
prepare your transceiver for low power output into a dummy load
(you may find your PTT unexpectedly comes on upon executing the
program).
Now run TOR. If your PTT comes on right away, the sense of RTS
must be inverted before further testing can be done (Try
outmask:2). Normally, TOR should put you in standby mode.
Next, on-the air tests will be necessary. Try to decode some FEC.
FEC will be decoded while in standby mode. To make sure that you
are in standby mode, hit F10. Tune in on an FEC transmission and
wait for it to sync. If it fails to decode anything, first try
changing the other sideband setting of your transceiver (if you
normally use LSB, try using USB). This will show whether it's the
interface logic or whether there is some other problem. If TOR
receives FEC in the other sideband setting, the sense of DCD
needs to be changed (Try inmask:1) and revert to your preferred
sideband setting (or RTTY setting if your transceiver has one).
The final test is to determine the logic level required for the
transmitted data. Try an ARQ call. If it fails, you need to
invert the sense of DTR (this will be either outmask:1 or
outmask:3 depending on the outcome of the RTS/PTT test above).
5.0 Operating PCTOR
Upon startup, the shareware banner will be displayed. Press any
key to proceed to the TOR screen.
TOR displays three windows: the status window, the received
traffic window, and the keyboard display.
CAUTION: PCTOR extends the function of the system timer. If TOR
is terminated abnormally the system clock may not be working
correctly. TOR may be exited normally by hitting two ESC
characters (the first ESC will take you into command mode, the
second will terminate TOR).
The smallest window. at the top of the screen, is the status
window. It is updated in real time and some machines may show
some flickering. This is normal.
Link status information is displayed on the left hand side of the
status line.
Adjacent to the link status is the selcal/callsign of the remote
station. This data is used in establishing the link and also for
printing out identification data (see usage of the "Ins" key).
Next, the transmit data delay is shown. You may change this
parameter using the command menu.
Once some traffic start flowing, the block receive time will be
displayed. This is an internal timing parameter that cannot be
changed.
A 24 hour-format clock is also shown on the display. This clock
will be used for timing and time stamps in future versions of the
software.
An eleven bit analog indicator on the right hand side shows how
bit phasing is progressing. During FEQ or ARQ, the indicator
should show slow motion from right to left. The speed of the
motion depends on how much your clock and the other station's are
differing relative to each other.
5.1 Function keys
The function keys have the following functions:
F1 - Initiate an ARQ call.
F2 - Initiate an FEC call.
F3 - Force a change-over (works only in ARQ).
F4 - Initiate QRT sequence (ends ARQ and FEC transmissions).
F5 - Not used.
F6 - Initiate ARQ listen mode.
F7 - Clear keyboard type ahead and special buffers (used for
WRU), clears keyboard display.
SHFT F7 - Clears receive display.
F8 - Force a system HALT. May restarted with F10.
F9 - Not used.
F10 - Abort any operation and revert to standby mode.
End - Enter the +? sequence into the keyboard buffer.
Ins - Enter an identification string into the keyboard buffer.
Del - Force LTR case during receive (FEC or ARQ).
ESC - Calls up the command menu when in user mode. When in
the Command menu, quits the program.
ALT-F - Enter the files menu. This allows a data file to be
loaded into the keyboard buffer.
ALT-C - Prompt user to enter the selcal/callsign of the remote
station AND initiate an ARQ call immediately.
ALT-R - Prompt user for the selcal/callsign of the remote station
WITHOUT initiating an ARQ call.
Command Menu
The command menu (called up when the ESC key is pressed when in
the main display) has the following one letter commands:
D - set the tx-delay
H - Help with the function keys
I - set your own ARQ identity
M - modify the interface logic masks
W - set up your WRU text
X - exit the command menu
ESC - terminate PCTOR
6.0 Principle of Operation
TORBIOS is a TSR software library that is installed as part of
DOS. The calling program usually installs it if it isn't there
already, also prevents it from being re-installed if it has been
loaded before. Two special versions of TORBIOS can be installed:
TORBIOS will interface with COM1 and TORBIOS2 will interface with
COM2. These programs is mutually exclusive as they both use the
same software entry point.
7.0 Disclaimer
The author, Johan Forrer KC7WW is not responsible for any damage,
injury, loss of profit or gain associated with the use,
installation, or application of this software.
October 1991
J.B.Forrer KC7WW
26553 Priceview Drive
Monroe, OR 97456
United States of America